Skip to content

Feature/freeze account implementation - #255

Closed
Akatenvictor wants to merge 8 commits into
StellarState:devfrom
Akatenvictor:feature/freeze-account-implementation
Closed

Feature/freeze account implementation#255
Akatenvictor wants to merge 8 commits into
StellarState:devfrom
Akatenvictor:feature/freeze-account-implementation

Conversation

@Akatenvictor

@Akatenvictor Akatenvictor commented Jul 27, 2026

Copy link
Copy Markdown

Description

Closes #
Closes #105
Closes #107
Closes #100
Closes #98

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📝 Documentation update
  • 🎨 UI/UX improvement
  • ♻️ Code refactoring
  • ✅ Test addition or update
  • 🔧 Configuration change

Checklist

  • My code follows the code style of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published

Testing

How to Test

  1. Step one
  2. Step two
  3. Step three

Test Coverage

  • Unit tests added/updated
  • Integration tests added/updated
  • E2E tests added/updated (if applicable)
  • Manual testing completed

Screenshots (if applicable)

Additional Notes

For Reviewers

  • Code quality and readability
  • Test coverage
  • Security implications
  • Performance impact
  • Breaking changes

chiscookeke11 and others added 8 commits July 26, 2026 04:58
@chiscookeke11
Add WASM release dry-run checks
52b5186
@chiscookeke11
Merge pull request StellarState#1 from chiscookeke11/codex/add-wasm-r…
9d7a4c8 
…elease-dry-run-workflow-step

Add WASM release dry-run and size checks to CI
@chiscookeke11
ci: add cargo audit vulnerability scanning
cb0d808
@chiscookeke11
Merge pull request StellarState#2 from chiscookeke11/codex/integrate-…
4846c88 
…cargo-audit-in-ci

ci: add cargo-audit vulnerability scanning
@chizzy192
Merge pull request StellarState#247 from chiscookeke11/issue-65
4e7bb18 
Add WASM release dry-run workflow step
@chizzy192
Merge branch 'main' into issue-66
0cc418c
@chizzy192
Merge pull request StellarState#248 from chiscookeke11/issue-66
7ed6dc0 
ci: add cargo-audit vulnerability scanning
Akatenvictor
feat: Add account freeze/unfreeze functionality
1e40bd5 
- Add Frozen storage key in types.rs
- Add AccountFrozen and AccountNotFrozen error variants
- Add account_frozen and account_unfrozen events
- Add storage functions for frozen accounts
- Implement freeze_account, unfreeze_account, and is_frozen functions
- Add frozen account checks to transfer and transfer_from
- Add comprehensive unit tests for freeze/unfreeze operations

Resolves: Token Freeze/Unfreeze Account Restrict Hooks
@drips-wave

drips-wave Bot commented Jul 27, 2026

Copy link
Copy Markdown

@Akatenvictor Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@chizzy192

chizzy192 commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Hi @Akatenvictor! 👋 Thank you for your contribution. CI checks are currently failing (2 failing checks). Please inspect the build errors and update your PR.

@chizzy192

chizzy192 commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Hi @Akatenvictor, please rebase your branch against dev to resolve storage conflicts in contracts/invoice-token/src/storage.rs. Fix the failing freeze account test assertions in test.rs and verify cargo test -p invoice-token builds cleanly.

@chizzy192

chizzy192 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Closing this PR to repurpose it as a fresh GitHub issue for the next contribution wave. Please pick up the corresponding issue and submit a clean PR targeting dev with all CI checks passing. Thank you!

@chizzy192 chizzy192 closed this Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

3 participants

@Akatenvictor @chizzy192 @chiscookeke11